-- The handler for "checkOneRight" is in the stack script.
on mouseUp
checkOneRight cd
end mouseUp
-- part 18 (button)
-- low flags: 00
-- high flags: A003
-- rect: left=273 top=311 right=329 bottom=391
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: Correct Answer
----- HyperTalk script -----
-- This handler shows the correct answer.
on mouseUp
resetCd
set hilite of btn "A1" to true
wait 25
repeat 2
set hilite of btn "A1" to false
wait 25
set hilite of btn "A1" to true
wait 25
end repeat
ans 4,cd
end mouseUp
-- part 22 (field)
-- low flags: 81
-- high flags: 0004
-- rect: left=8 top=165 right=317 bottom=140
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 0
-- font id: 174
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: Feedback
----- HyperTalk script -----
on mouseUp
hide me
end mouseUp
-- part contents for background part 9
----- text -----
3 of 5
-- part contents for background part 19
----- text -----
Good. HyperCard is sounding more and more like the flexible solution to our problem.
That makes it sound like I can’t easily incorporate new information. I don’t want to have to just tack it on. Can’t I just make changes to what’s already there?
I do? ... Hmm. I guess I’ll have to keep looking, then.
This is the correct answer. He needs to know that he can update existing cards.
-- part contents for background part 31
----- text -----
No. You can resize text fields at any time to accomodate new information (or change field styles), and you can enter new information at any time, without having to recreate the whole stack.
No. You can make new cards to hold the information, or build new stacks at any time that will hold any overflow.